When you attempt to configure and deploy SAS Business Intelligence Portlets using the SAS^® Deployment Wizard, the following errors might occur:

The following problem was encountered while configuring SAS BI Portlets:
failed to deploy Ear sas.biportlets4.2.ear. Return status:   
${weblogic.deploy}

In addition, the following errors appear in the biportlets_deployWebapps_2009-10-02-14.28.42.log file, the Web application-server administration log, the SASServer1 log, and the RemoteServices.log file:

• For biportlets_deployWebapps_2009-10-02-14.28.42.log:

  BUILD FAILED
  ...more error messages. . .
  d:\Program Files\SAS92\SASDeploymentManager\9.2 
  \products\cfgwizard_92300_prt_xx_sp0_1\
  Utilities\webAppAntTasks–weblogic.xml:1332: failed to deploy Ear  
  sas.biportlets4.2.ear.  Return status: ${weblogic.deployEAR}
  

• For the Web application-server administration log:

  <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating 
  deploy task for application 'sas.biportlets4.2.ear'.> 
  <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
  weblogic.application.ModuleException: 
  	at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
  	at weblogic.servlet.internal.WebAppModule.start
             (WebAppModule.java:468)
  	at weblogic.application.internal.flow.ModuleStateDriver$3.next
             (ModuleStateDriver.java:204)
  	at weblogic.application.utils.StateMachineDriver.nextState
             (StateMachineDriver.java:37)
  	at weblogic.application.internal.flow.ModuleStateDriver.start
             (ModuleStateDriver.java:60)
  	Truncated. see log file for complete stacktrace
  java.lang.SecurityException: Authentication failed
  	at org.jgroups.protocols.pbcast.ClientGmsImpl.join
             (ClientGmsImpl.java:133)
  	at org.jgroups.protocols.pbcast.GMS.down(GMS.java:801)
  	at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
  	at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
  	at org.jgroups.protocols.pbcast.STATE_TRANSFER.down
             (STATE_TRANSFER.java:294)
  	Truncated. see log file for complete stacktrace
  

• For the SASServer1 log:

  Error creating bean with name 'sas.svcs.cache' defined in class path resource
  [config-context.xml]: Instantiation of bean failed; nested exception is
  org.springframework.beans.BeanInstantiationException: Could not instantiate
  bean class [com.sas.svcs.cluster.SimpleCache]: Constructor threw exception; 
  nested exception is java.lang.IllegalStateException: Unable to start 
  distributed cache.
  

• For RemoteServices.log:

  [IncomingPacketHandler (channel=SimpleCacheGroup)] WARN []
  org.jgroups.auth.SimpleToken – Authentication failed on SimpleToken
  [IncomingPacketHandler (channel=SimpleCacheGroup)] WARN  []
  org.jgroups.protocols.AUTH – AUTH failed to validate AuthHeader token
  

The errors listed above occur if you enable an authentication token for multicast during the configuration.

The workaround for the issue is as follows:

1. Stop the Remote Services and SASServer1.
2. Either rename the log files or remove them.
3. Modify the web.xml file for both of the .war files (sas.biportlets4.2.war and sas.jsr168remoteportlet4.2.war) that are included in the deployed instance of the sas.biportlets4.2.ear file. The web.xml files for both of these applications are located in the following directories:
   • SAS_configuration_directory\Lev1\Web\Staging\exploded\sas.biportlets4.2.ear\sas.biportlets4.2.war\WEB-INF\web.xml
   • SAS_configuration_directory\Lev1\Web\Staging\exploded\sas.biportlets4.2.ear\sas.jsr168remoteportlet4.2.war\WEB-INF\web.xml.

   To modify the web.xml files, change the value of the parentContextKey element from config.context to secure.config.context, as shown in this example:

<context-param> <param-name>parentContextKey</param-name> <param-value>secure.config.context</param-value> </context-param>
4. Restart Remote Services and SASServer1.

Notes:

• Depending on your application server, you might need to do the following:
  1. Unzip (explode) the biportlets.ear file and make your changes. Then rezip (implode) the file.
  2. Undeploy the current biportlets.ear file from the Web application server and deploy the newly created .ear file.
• You must apply the changes described in the workaround above each time the biportlets.ear file is built.
• A fix for this issue is planned for a later release of SAS Business Intelligence Portlets.

Operating System and Release Information